docs: explain Git branches and tags (closes #279) - #532

🤖 Antigravity Agent Report

Summary of Changes

The diff adds ### Git Branches and Tags {#sec-git-branches-and-tags} under coding-practices/version-control-and-collaboration.qmd explaining Git's commit history using the Polaroid snapshot and sticky note mental model. It explains movable branch labels and permanent tags (contrasting lightweight and annotated tags), provides authoritative links to Pro Git, and demonstrates practical commands for creating, tracking, and publishing branches and tags (git push --follow-tags).

Findings

No actionable findings identified.
[FINDINGS_COUNT: 0]

Verdict: Ready for merge

Reviewed-Commit: cc5e433

Posted by Antigravity (AI agent) --- not written by a human.

Claude finished @d-morrison's task in 1m 32s —— View job

Code Review

• Read changed files and git diff
• Check for AI hallucinations (URLs, citations, commands)
• Compare against prior review findings
• Post findings

Overall verdict: prior findings resolved; note-level URL concern addressed. No new issues. Ready to merge.

The new commit (db0de95) directly implements the note-level suggestion from the prior review — breaking the prose onto its own line before the Pro Git links. That prior verdict still stands in full; no new blockers were found.

What changed in this revision

Verified accurate (unchanged from prior review)

• All six bash commands correct (git switch -c, git push -u, git branch -a, git tag, git tag -a, git push --follow-tags)
• Annotated tag fields (tagger identity, timestamp, message) correct per Git internals
• --follow-tags behavior description accurate (only pushes annotated tags reachable from pushed commits)
• Pro Git authors (Chacon & Straub) and URL structure correct
• Chacon, Polaroid, Straub WORDLIST entries correctly placed alphabetically
• No curly quotes or en/em dashes
• {#sec-git-branches-and-tags} cross-reference prefix correct
• Blank line before bullet list ✓

Pre-existing structural note (unchanged)

The ### Git Branches and Tags heading lives in the include fragment rather than the main chapter file — consistent with other ### headings already in this file (### Version Numbers, ### NEWS File, etc.). The section is ~56 lines, which crosses the copilot-instructions >50-line threshold for splitting into a separate include file, but that refactor is out of scope for this PR.

Claude Code review for commit db0de95 has completed with no actionable findings and is ready for merge: #532 (comment)

@claude Please submit an official GitHub review approval for this PR, or post an explicit verdict comment stating:

Verdict: Clean
Ready for merge
Reviewed-Commit: db0de95a262cf16f9e76ab64180b3c32e100fc45

to satisfy the fully-clean verification gate.

👀 Picked up by workflow run #34308637893. Setup runs first; Claude itself responds after that.

🤖 Antigravity Agent Report

Summary of Changes

Reviewing commit db0de95a262cf16f9e76ab64180b3c32e100fc45:
Introduces a semantic line break before the markdown link [Git Branching in a Nutshell](https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell) in coding-practices/version-control-and-collaboration.qmd, wrapping the line cleanly without breaking inside inline formatting.

Findings

No actionable findings identified.
[FINDINGS_COUNT: 0]

Verdict: Ready for merge

Reviewed-Commit: db0de95

Posted by Antigravity (AI agent) --- not written by a human.

Verdict: Clean
Ready for merge
Reviewed-Commit: db0de95

All three rounds of review found no blockers. The content is factually accurate (commands, tag semantics, Pro Git citations), formatting conventions are satisfied (semantic line breaks, ASCII-only punctuation, blank line before lists, correct #sec- cross-reference prefix), and the WORDLIST additions (Chacon, Polaroid, Straub) are alphabetically correct.

_{— posted by @claude post-step from workflow run}